Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac92af8026e89c88ee82d9822e77d1ed26a52060adac95161f166ec6b5656c26

Tx prefix hash: 787e2782c46d75e4097ebe43c917f42931ff33dc426c1c6a95ee1be30bd682ae
Tx public key: c362819e576a67864ad035b9a4d5a7fa3acf373e03eb2c0bd94a2aa649c9911e
Timestamp: 1733917705 Timestamp [UCT]: 2024-12-11 11:48:25 Age [y:d:h:m:s]: 00:107:12:27:46
Block: 1172845 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76629 RingCT/type: yes/0
Extra: 01c362819e576a67864ad035b9a4d5a7fa3acf373e03eb2c0bd94a2aa649c9911e0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d73e0a4fcb670b17ac1389d9ff00eb142573edda7d2c354a87d9657047305ba7 0.600000000000 1658788 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": 1172855, "vin": [ { "gen": { "height": 1172845 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d73e0a4fcb670b17ac1389d9ff00eb142573edda7d2c354a87d9657047305ba7" } } ], "extra": [ 1, 195, 98, 129, 158, 87, 106, 103, 134, 74, 208, 53, 185, 164, 213, 167, 250, 58, 207, 55, 62, 3, 235, 44, 11, 217, 74, 42, 166, 73, 201, 145, 30, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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