Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 864adf2c864eed3aba66601f4b08da30544a273e0a104e568fe42b8169631f68

Tx prefix hash: 2238997139fd20f40661408e99f699e0416e4e2518ab5914f068c6f7e89691c0
Tx public key: 2d1aaf57cbe7a2284877dc82e01e5e546ec17af7096e10a2164df9c59fa1b1ef
Timestamp: 1737460720 Timestamp [UCT]: 2025-01-21 11:58:40 Age [y:d:h:m:s]: 00:148:05:19:55
Block: 1202121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105672 RingCT/type: yes/0
Extra: 012d1aaf57cbe7a2284877dc82e01e5e546ec17af7096e10a2164df9c59fa1b1ef021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 15ac3d7e93fdb421e27dd8f07f0c4d732ec959dd65f303f7853c58b911cf261f 0.600000000000 1688780 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": 1202131, "vin": [ { "gen": { "height": 1202121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "15ac3d7e93fdb421e27dd8f07f0c4d732ec959dd65f303f7853c58b911cf261f" } } ], "extra": [ 1, 45, 26, 175, 87, 203, 231, 162, 40, 72, 119, 220, 130, 224, 30, 94, 84, 110, 193, 122, 247, 9, 110, 16, 162, 22, 77, 249, 197, 159, 161, 177, 239, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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