Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8068a245199873c09985b0252972f25ebca2c6549fddcf2fef5fc672fe833a36

Tx prefix hash: 89ee162fbb4cf62f6c4ea7a8f8d10ff83949434be8e6da02e7ae123ac7fd8ca1
Tx public key: b168df179b629276defd079b9ecedca3f7d84e4e1bee4e0d6984aef04e697232
Timestamp: 1726367389 Timestamp [UCT]: 2024-09-15 02:29:49 Age [y:d:h:m:s]: 01:055:04:49:23
Block: 1110341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297865 RingCT/type: yes/0
Extra: 01b168df179b629276defd079b9ecedca3f7d84e4e1bee4e0d6984aef04e69723202110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e63cc05610fa9149347036f33229b7c5ccafcadbce503fbb43456caa42aeb2c1 0.600000000000 1588910 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": 1110351, "vin": [ { "gen": { "height": 1110341 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e63cc05610fa9149347036f33229b7c5ccafcadbce503fbb43456caa42aeb2c1" } } ], "extra": [ 1, 177, 104, 223, 23, 155, 98, 146, 118, 222, 253, 7, 155, 158, 206, 220, 163, 247, 216, 78, 78, 27, 238, 78, 13, 105, 132, 174, 240, 78, 105, 114, 50, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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