Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1a5840f59a3ad6de60f73d8a4753323d0b738fd5f4cc934bc792e7feef99da7

Tx prefix hash: 84a3832dafcc696bc03a014f7ed8d37b94f124f9eecc76c4b13917f733f058c7
Tx public key: bd22c3542d830334603bafead979f9dd7e25fc3259365775931213c8aba6fb86
Timestamp: 1750928601 Timestamp [UTC]: 2025-06-26 09:03:21 Age [y:d:h:m:s]: 01:140:01:23:43
Block: 1313084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364240 RingCT/type: yes/0
Extra: 01bd22c3542d830334603bafead979f9dd7e25fc3259365775931213c8aba6fb86021100000004a11dba98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8cc47eee7cc6f9a3a14f1d95d0cab390b168239be7dfba20bcbabb8f65970b58 0.000600000000 1800721 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": 1313094, "vin": [ { "gen": { "height": 1313084 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8cc47eee7cc6f9a3a14f1d95d0cab390b168239be7dfba20bcbabb8f65970b58" } } ], "extra": [ 1, 189, 34, 195, 84, 45, 131, 3, 52, 96, 59, 175, 234, 217, 121, 249, 221, 126, 37, 252, 50, 89, 54, 87, 117, 147, 18, 19, 200, 171, 166, 251, 134, 2, 17, 0, 0, 0, 4, 161, 29, 186, 152, 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: