Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e7217e6eb61091f52aa7b1ea897a3adcefd89b61c3da32cb8d3b8b6c7d7baad

Tx prefix hash: b58e25ca201a0a0fe36a2afd547d1b419aecf7e92f1637f5dad39ae3ad79c4d7
Tx public key: deb6e9ba440fdfab47799c7a7ca3cdf4b7f054137b420982a8ba127e3cb7bf70
Timestamp: 1772804472 Timestamp [UTC]: 2026-03-06 13:41:12 Age [y:d:h:m:s]: 00:257:03:22:45
Block: 1491966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189299 RingCT/type: yes/0
Extra: 01deb6e9ba440fdfab47799c7a7ca3cdf4b7f054137b420982a8ba127e3cb7bf7002110000000bf188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f9fbe36732666166142a68221d4b759bf6134b823e0903f155c6b2aaf3294ed2 0.000600000000 1981504 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": 1491976, "vin": [ { "gen": { "height": 1491966 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9fbe36732666166142a68221d4b759bf6134b823e0903f155c6b2aaf3294ed2" } } ], "extra": [ 1, 222, 182, 233, 186, 68, 15, 223, 171, 71, 121, 156, 122, 124, 163, 205, 244, 183, 240, 84, 19, 123, 66, 9, 130, 168, 186, 18, 126, 60, 183, 191, 112, 2, 17, 0, 0, 0, 11, 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: