Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 559c46b258a4cb47de4e3334677cc37e4ea48d93fec618f192bf1abe4ac92511

Tx prefix hash: facf76e2c79e1025c45c0b7e865be9fc05fd0f659cf006a911c52b29c6c41a0b
Tx public key: a9d890e7b1eb20969788119239140d34557dd60329c618f25bbe41c9d4d827b2
Timestamp: 1703486573 Timestamp [UCT]: 2023-12-25 06:42:53 Age [y:d:h:m:s]: 01:173:04:40:28
Block: 920650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384851 RingCT/type: yes/0
Extra: 01a9d890e7b1eb20969788119239140d34557dd60329c618f25bbe41c9d4d827b20211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a6f1897cdf14fc11e0bb917657b56a2b951c227a2a168e9ba42deca3ac2d1d2 0.600000000000 1378330 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": 920660, "vin": [ { "gen": { "height": 920650 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a6f1897cdf14fc11e0bb917657b56a2b951c227a2a168e9ba42deca3ac2d1d2" } } ], "extra": [ 1, 169, 216, 144, 231, 177, 235, 32, 150, 151, 136, 17, 146, 57, 20, 13, 52, 85, 125, 214, 3, 41, 198, 24, 242, 91, 190, 65, 201, 212, 216, 39, 178, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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