Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 210e2eb796bb3743df247f20f2bbae021a12d5f2b9fdcde59344a9841488ffb7

Tx prefix hash: 660a5bfb3b7c39cfd98d290e881a279716f3f53216d9adf84d0d384aee18124e
Tx public key: 17819b80f5cffa371ef4e08a830246fccaa4debd29e9c5b4e2a6ba28ff2b0d92
Timestamp: 1774561821 Timestamp [UTC]: 2026-03-26 21:50:21 Age [y:d:h:m:s]: 00:235:21:40:37
Block: 1506489 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174103 RingCT/type: yes/0
Extra: 0117819b80f5cffa371ef4e08a830246fccaa4debd29e9c5b4e2a6ba28ff2b0d92021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d3a4277494972628999fa69aec01e240b2f1f3dde8b83652a2ae968f3c9c1fe2 0.000600000000 1996233 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": 1506499, "vin": [ { "gen": { "height": 1506489 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3a4277494972628999fa69aec01e240b2f1f3dde8b83652a2ae968f3c9c1fe2" } } ], "extra": [ 1, 23, 129, 155, 128, 245, 207, 250, 55, 30, 244, 224, 138, 131, 2, 70, 252, 202, 164, 222, 189, 41, 233, 197, 180, 226, 166, 186, 40, 255, 43, 13, 146, 2, 17, 0, 0, 0, 2, 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: