Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cab0128a09697382d312c3b6f30953acf012905f22e36bf203fec7f23aff26dc

Tx prefix hash: 16ef24fbe77f224a38dac7b09d651fee75b669ef57418084a3d2128ef482ac01
Tx public key: 1d1bf6fa0d576969c8c1233e1f2d3a568528bd40ca0bd35d10673056657a7df4
Timestamp: 1706724587 Timestamp [UCT]: 2024-01-31 18:09:47 Age [y:d:h:m:s]: 01:095:12:35:00
Block: 947474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329365 RingCT/type: yes/0
Extra: 011d1bf6fa0d576969c8c1233e1f2d3a568528bd40ca0bd35d10673056657a7df402110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fba0d7402b550943d57480e1ad43eecfc05a8b364ba33f30a8e2a2db857db6ac 0.600000000000 1405824 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": 947484, "vin": [ { "gen": { "height": 947474 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fba0d7402b550943d57480e1ad43eecfc05a8b364ba33f30a8e2a2db857db6ac" } } ], "extra": [ 1, 29, 27, 246, 250, 13, 87, 105, 105, 200, 193, 35, 62, 31, 45, 58, 86, 133, 40, 189, 64, 202, 11, 211, 93, 16, 103, 48, 86, 101, 122, 125, 244, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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