Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56c66f3fa86212b559756635a6a98767a8d1ee4e7d76a1c0119ded4e094c692c

Tx prefix hash: 649a1e38bedf72ffa800feeeac2868b93914614f0deb69bbfea3912035854c15
Tx public key: 548678d7307ff814c754c71fd7025c2c211eb16ee5a6f31d7a178dc60b7bf14f
Timestamp: 1774052798 Timestamp [UTC]: 2026-03-21 00:26:38 Age [y:d:h:m:s]: 00:239:13:44:23
Block: 1502265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176679 RingCT/type: yes/0
Extra: 01548678d7307ff814c754c71fd7025c2c211eb16ee5a6f31d7a178dc60b7bf14f021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 29709ebdc81613d4422b0a2b4a6a5ff6e3764b5bb3a291ac4866beaacff26a13 0.000600000000 1991959 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": 1502275, "vin": [ { "gen": { "height": 1502265 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29709ebdc81613d4422b0a2b4a6a5ff6e3764b5bb3a291ac4866beaacff26a13" } } ], "extra": [ 1, 84, 134, 120, 215, 48, 127, 248, 20, 199, 84, 199, 31, 215, 2, 92, 44, 33, 30, 177, 110, 229, 166, 243, 29, 122, 23, 141, 198, 11, 123, 241, 79, 2, 17, 0, 0, 0, 2, 228, 245, 25, 63, 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: