Dinastycoin Explorer Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 465ddfcc1fc9f0437aa6a208dcad1e2b946a35b0f3c5cb133e9ec73ee222d7d1

Tx prefix hash: 954de023a4ff909556ff849eec471555b9e1fbf336f44ddc2c956d69aba8c4da
Tx public key: cdc2518f381c9efa4f59e9eae2bf790a101631047290590ea01f1bd111d81375
Timestamp: 1774006664 Timestamp [UTC]: 2026-03-20 11:37:44 Age [y:d:h:m:s]: 00:059:20:38:02
Block: 1501888 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36233 RingCT/type: yes/0
Extra: 01cdc2518f381c9efa4f59e9eae2bf790a101631047290590ea01f1bd111d81375021100000006f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d596800ac7fd3227cf32b861c830925f8e0e41aee8c23e552a8d163647bed0fd 0.000600000000 1991580 of 15 -

Check which outputs belong to given dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinastycoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1501898, "vin": [ { "gen": { "height": 1501888 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d596800ac7fd3227cf32b861c830925f8e0e41aee8c23e552a8d163647bed0fd" } } ], "extra": [ 1, 205, 194, 81, 143, 56, 28, 158, 250, 79, 89, 233, 234, 226, 191, 121, 10, 16, 22, 49, 4, 114, 144, 89, 14, 160, 31, 27, 209, 17, 216, 19, 117, 2, 17, 0, 0, 0, 6, 241, 136, 200, 168, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: