Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad53048c469e437a1ffc5f8e61c6a7d8ececde74008c8a7e3408dd6d9b2a6ea9

Tx prefix hash: a31658be6772a18426fc79506fc8e787fb0fcd0f18c7dd1c0a381e38c85d76a7
Tx public key: f538937db941b66ebca16c3901f744f9e70caf1b19e5cf86b92158b5b86ca933
Timestamp: 1763015267 Timestamp [UCT]: 2025-11-13 06:27:47 Age [y:d:h:m:s]: 00:051:04:17:29
Block: 1411047 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36657 RingCT/type: yes/0
Extra: 01f538937db941b66ebca16c3901f744f9e70caf1b19e5cf86b92158b5b86ca933021100000005dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29741ddba4fd8f18534a8af51d10d7e09df12009505938111d99ff1f18ae79b2 0.600000000000 1899504 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 dinasty-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": 1411057, "vin": [ { "gen": { "height": 1411047 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29741ddba4fd8f18534a8af51d10d7e09df12009505938111d99ff1f18ae79b2" } } ], "extra": [ 1, 245, 56, 147, 125, 185, 65, 182, 110, 188, 161, 108, 57, 1, 247, 68, 249, 231, 12, 175, 27, 25, 229, 207, 134, 185, 33, 88, 181, 184, 108, 169, 51, 2, 17, 0, 0, 0, 5, 223, 195, 186, 73, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8