Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19e589dfe133400a389dd494f24ba252c0ecd475e12dbf810deb036e10bc4795

Tx prefix hash: 95b6e4e9baf9baf30992c6b04cbfe79df1baaa590d84d0320d7d15a98fc9aabb
Tx public key: 0d397c02f98bf4aa2ebc438873d9362d4f3959c8a3a916f8f732794af62819d1
Timestamp: 1773517569 Timestamp [UTC]: 2026-03-14 19:46:09 Age [y:d:h:m:s]: 00:245:03:59:12
Block: 1497876 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180616 RingCT/type: yes/0
Extra: 010d397c02f98bf4aa2ebc438873d9362d4f3959c8a3a916f8f732794af62819d1021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 912db2a870eddede08cf63b754c3cba97dc4a9c6ce27c1b8726f7f261af2bd32 0.000600000000 1987518 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": 1497886, "vin": [ { "gen": { "height": 1497876 } } ], "vout": [ { "amount": 600000000, "target": { "key": "912db2a870eddede08cf63b754c3cba97dc4a9c6ce27c1b8726f7f261af2bd32" } } ], "extra": [ 1, 13, 57, 124, 2, 249, 139, 244, 170, 46, 188, 67, 136, 115, 217, 54, 45, 79, 57, 89, 200, 163, 169, 22, 248, 247, 50, 121, 74, 246, 40, 25, 209, 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: