Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c518dafcf143b3bad7476c5c6c7dadab6eca95f59cf3c8fa1ffc11669f1d6463

Tx prefix hash: a44deb74c6eca8617ae7f95d16d374836908a1a6bb362579c2fe79ad7742004c
Tx public key: ddda1c1c24db8cec758af09a363d4679a0550a800f0d5259e5034d472ce13d0f
Timestamp: 1703016691 Timestamp [UCT]: 2023-12-19 20:11:31 Age [y:d:h:m:s]: 01:110:08:33:52
Block: 916766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339973 RingCT/type: yes/0
Extra: 01ddda1c1c24db8cec758af09a363d4679a0550a800f0d5259e5034d472ce13d0f021100000003e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd52228d0eba3b6ae617bae15a93e4850fa3f8b5f708b1fcdd8b89d4c1e57b40 0.600000000000 1374326 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": 916776, "vin": [ { "gen": { "height": 916766 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd52228d0eba3b6ae617bae15a93e4850fa3f8b5f708b1fcdd8b89d4c1e57b40" } } ], "extra": [ 1, 221, 218, 28, 28, 36, 219, 140, 236, 117, 138, 240, 154, 54, 61, 70, 121, 160, 85, 10, 128, 15, 13, 82, 89, 229, 3, 77, 71, 44, 225, 61, 15, 2, 17, 0, 0, 0, 3, 228, 187, 107, 131, 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