Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01fb5d47481bfa60d5d84b7352ef6aaeda2f5f6b01c07a6009a11e4eafdbf3f3

Tx prefix hash: 99ed3d68338ea9d6883e4ff7f4a0a19119f5cdb4ee7631883cb98bbb9bf14bd2
Tx public key: baec3a7f9233442f8c37585e1033000e1673f4b3c2f5b81ce2c6eb8f5fd54d72
Timestamp: 1742824974 Timestamp [UTC]: 2025-03-24 14:02:54 Age [y:d:h:m:s]: 01:235:01:48:06
Block: 1246301 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 431941 RingCT/type: yes/0
Extra: 01baec3a7f9233442f8c37585e1033000e1673f4b3c2f5b81ce2c6eb8f5fd54d7202110000000524ff4ea1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 31c8477d8cc0ec1b225437445349015901324fba9e4eae70128343f6cbb06f66 0.000600000000 1733302 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": 1246311, "vin": [ { "gen": { "height": 1246301 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31c8477d8cc0ec1b225437445349015901324fba9e4eae70128343f6cbb06f66" } } ], "extra": [ 1, 186, 236, 58, 127, 146, 51, 68, 47, 140, 55, 88, 94, 16, 51, 0, 14, 22, 115, 244, 179, 194, 245, 184, 28, 226, 198, 235, 143, 95, 213, 77, 114, 2, 17, 0, 0, 0, 5, 36, 255, 78, 161, 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: