Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05430e6c5e91d18db2fedba5caa70eab90e8b244a8670f36afd3d8508573a6d6

Tx prefix hash: 04359bf0469d14c58962089f1e195ce222353677e2b849b7a9564c804fb07784
Tx public key: cdf5e48e99097543a2fba6e9d4bccff6eaccb7ef6cbe7285245541dd18d59f4e
Timestamp: 1773196764 Timestamp [UTC]: 2026-03-11 02:39:24 Age [y:d:h:m:s]: 00:254:15:48:18
Block: 1495206 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187655 RingCT/type: yes/0
Extra: 01cdf5e48e99097543a2fba6e9d4bccff6eaccb7ef6cbe7285245541dd18d59f4e021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4d245a3f6811aa48e7a3cc4d89d0478d86261c94e196ab3d54ea9d059b02deb4 0.000600000000 1984816 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": 1495216, "vin": [ { "gen": { "height": 1495206 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d245a3f6811aa48e7a3cc4d89d0478d86261c94e196ab3d54ea9d059b02deb4" } } ], "extra": [ 1, 205, 245, 228, 142, 153, 9, 117, 67, 162, 251, 166, 233, 212, 188, 207, 246, 234, 204, 183, 239, 108, 190, 114, 133, 36, 85, 65, 221, 24, 213, 159, 78, 2, 17, 0, 0, 0, 1, 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: