Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cdc64d3512333d47bbaf5a8206eb64401658373f83385a556f9a219e23c401ad

Tx prefix hash: 675a5b889019e526259f4b83ada880a8bd03c7c95d8709c2e0c8ed4d4737a256
Tx public key: e47ee7a00bac9575f16959c6fc32f0c1f9cabce1e3a6f802b0223d1f39d08c31
Timestamp: 1747090462 Timestamp [UCT]: 2025-05-12 22:54:22 Age [y:d:h:m:s]: 00:192:15:14:32
Block: 1281614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135381 RingCT/type: yes/0
Extra: 01e47ee7a00bac9575f16959c6fc32f0c1f9cabce1e3a6f802b0223d1f39d08c310211000000011f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72a98e1e589933f51d9562544546bf835c1c1855a53121f013fdecf5a6b9bad8 0.600000000000 1769013 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": 1281624, "vin": [ { "gen": { "height": 1281614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72a98e1e589933f51d9562544546bf835c1c1855a53121f013fdecf5a6b9bad8" } } ], "extra": [ 1, 228, 126, 231, 160, 11, 172, 149, 117, 241, 105, 89, 198, 252, 50, 240, 193, 249, 202, 188, 225, 227, 166, 248, 2, 176, 34, 61, 31, 57, 208, 140, 49, 2, 17, 0, 0, 0, 1, 31, 144, 81, 122, 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