Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a795f8e645ed45094d004e81cd3069653b66cb1713c494a2d292c9e1a12b3402

Tx prefix hash: c5bae83df66b7576c29532b6da04c356175f968fc0c4c2596f8d682e2ff917b9
Tx public key: c7d66bdf7035b40f0df5d547bb9bb58045b1fc52ccf334707589807d981c5a42
Timestamp: 1725730002 Timestamp [UCT]: 2024-09-07 17:26:42 Age [y:d:h:m:s]: 00:222:21:31:10
Block: 1105064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159154 RingCT/type: yes/0
Extra: 01c7d66bdf7035b40f0df5d547bb9bb58045b1fc52ccf334707589807d981c5a42021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a475db0f7ee683eb179a1f5e38f05b1583102e926ad9cf468e98dff821c3ae7 0.600000000000 1582401 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": 1105074, "vin": [ { "gen": { "height": 1105064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a475db0f7ee683eb179a1f5e38f05b1583102e926ad9cf468e98dff821c3ae7" } } ], "extra": [ 1, 199, 214, 107, 223, 112, 53, 180, 15, 13, 245, 213, 71, 187, 155, 181, 128, 69, 177, 252, 82, 204, 243, 52, 112, 117, 137, 128, 125, 152, 28, 90, 66, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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