Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddf09ad27fe570ad78599e2da0e2898eb90e1cebf1e72366aebabd2f4851d8c2

Tx prefix hash: 373bf87af41f738c698d64bbca7e6f3d7e09678de84fbe15907dc69207df11d5
Tx public key: ee2c94223a4d033e341f370379da9814c2aa237e6ec601c216e9ebad38f44e99
Timestamp: 1729605594 Timestamp [UCT]: 2024-10-22 13:59:54 Age [y:d:h:m:s]: 00:185:13:50:50
Block: 1137153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132446 RingCT/type: yes/0
Extra: 01ee2c94223a4d033e341f370379da9814c2aa237e6ec601c216e9ebad38f44e990211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a81c2160aaa1cbf4cdb178b4c6e2b91d9a8033cbe018deef47f69096531f53a4 0.600000000000 1620592 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": 1137163, "vin": [ { "gen": { "height": 1137153 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a81c2160aaa1cbf4cdb178b4c6e2b91d9a8033cbe018deef47f69096531f53a4" } } ], "extra": [ 1, 238, 44, 148, 34, 58, 77, 3, 62, 52, 31, 55, 3, 121, 218, 152, 20, 194, 170, 35, 126, 110, 198, 1, 194, 22, 233, 235, 173, 56, 244, 78, 153, 2, 17, 0, 0, 0, 1, 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