Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4644eb51683ed2e7adcf9e1e869e8d32a01411d7e74b55fd2cf0855a33c20f8d

Tx prefix hash: 9927d723a8e82e763ec8306f37bb08989e831e735c28e12d64de03998c15da3e
Tx public key: 659b5c40abde5d10ebfe53fc8e31fbf884bfc12d84c3785c55b7d7ad3aef635e
Timestamp: 1704096057 Timestamp [UCT]: 2024-01-01 08:00:57 Age [y:d:h:m:s]: 01:091:00:51:27
Block: 925695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326171 RingCT/type: yes/0
Extra: 01659b5c40abde5d10ebfe53fc8e31fbf884bfc12d84c3785c55b7d7ad3aef635e021100000005ac328d11000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ddfae14e5e1bc012e217184c90d766d99f24760ab5a9bfa7556de12b36fbefc9 0.600000000000 1383461 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": 925705, "vin": [ { "gen": { "height": 925695 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ddfae14e5e1bc012e217184c90d766d99f24760ab5a9bfa7556de12b36fbefc9" } } ], "extra": [ 1, 101, 155, 92, 64, 171, 222, 93, 16, 235, 254, 83, 252, 142, 49, 251, 248, 132, 191, 193, 45, 132, 195, 120, 92, 85, 183, 215, 173, 58, 239, 99, 94, 2, 17, 0, 0, 0, 5, 172, 50, 141, 17, 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