Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30045c82dd867d7afa3a06cbca7d8940e4adcab7082a0286d76708c6a3d8bbe9

Tx prefix hash: a9d1dfeb0b6216bf761820651d69a94388d1c512a97d5ea49c1e11ee575fa0aa
Tx public key: 8a5546bbc10fd3bef12253144b7c2f74667d3f65b4d18f9cf88c7cbe7cb9a154
Timestamp: 1724105198 Timestamp [UTC]: 2024-08-19 22:06:38 Age [y:d:h:m:s]: 02:091:22:04:45
Block: 1091591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 590535 RingCT/type: yes/0
Extra: 018a5546bbc10fd3bef12253144b7c2f74667d3f65b4d18f9cf88c7cbe7cb9a15402110000000391e13c04000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ccda9be92c137e5af8ab98493d9be008507c7866d01174794614a50b503ea3b5 0.000600000000 1566224 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": 1091601, "vin": [ { "gen": { "height": 1091591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ccda9be92c137e5af8ab98493d9be008507c7866d01174794614a50b503ea3b5" } } ], "extra": [ 1, 138, 85, 70, 187, 193, 15, 211, 190, 241, 34, 83, 20, 75, 124, 47, 116, 102, 125, 63, 101, 180, 209, 143, 156, 248, 140, 124, 190, 124, 185, 161, 84, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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: