Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6044637a027b471a84eb54ee0dc4b041d42e6e478c19b5d9966b2cb6a7395071

Tx prefix hash: fb27762ae606d015b1651a35bc242d1ed72ba0bd4d3768e66b8b77e3afb37964
Tx public key: 1c662f57d2be89beb73e599ee79b4b014278a53f6735c39304f4b5a8291dcd90
Timestamp: 1717568820 Timestamp [UCT]: 2024-06-05 06:27:00 Age [y:d:h:m:s]: 00:283:16:51:20
Block: 1037406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202766 RingCT/type: yes/0
Extra: 011c662f57d2be89beb73e599ee79b4b014278a53f6735c39304f4b5a8291dcd9002110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 590f864d27e29aff6a6eabc951ab3155f5839bf288c9f581211af2d9c49c3fb3 0.600000000000 1505937 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": 1037416, "vin": [ { "gen": { "height": 1037406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "590f864d27e29aff6a6eabc951ab3155f5839bf288c9f581211af2d9c49c3fb3" } } ], "extra": [ 1, 28, 102, 47, 87, 210, 190, 137, 190, 183, 62, 89, 158, 231, 155, 75, 1, 66, 120, 165, 63, 103, 53, 195, 147, 4, 244, 181, 168, 41, 29, 205, 144, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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