Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3051ee0bd2fb2cbaab53b02a035c1950b987e30b1f80531dc8f4870d8d30e9eb

Tx prefix hash: db4f156a46f923bdcc3422212c0765e314a0ae6dc1602900b6e33c14bd8992d2
Tx public key: 6a5928d1c62e3fe350fce60657b628e0b95a2d97435013a7998f147b75140eef
Timestamp: 1742802079 Timestamp [UTC]: 2025-03-24 07:41:19 Age [y:d:h:m:s]: 01:238:00:22:19
Block: 1246111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 434139 RingCT/type: yes/0
Extra: 016a5928d1c62e3fe350fce60657b628e0b95a2d97435013a7998f147b75140eef021100000005c6740958000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e206bf0c02d0e4c1967035f72a1c3ba27d8678c4e37c349d300957cb0b05d753 0.000600000000 1733106 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": 1246121, "vin": [ { "gen": { "height": 1246111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e206bf0c02d0e4c1967035f72a1c3ba27d8678c4e37c349d300957cb0b05d753" } } ], "extra": [ 1, 106, 89, 40, 209, 198, 46, 63, 227, 80, 252, 230, 6, 87, 182, 40, 224, 185, 90, 45, 151, 67, 80, 19, 167, 153, 143, 20, 123, 117, 20, 14, 239, 2, 17, 0, 0, 0, 5, 198, 116, 9, 88, 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: