Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22a70de22a6b58345237cfac7be52af613ad9d5858f0926ac4f41a9b50565753

Tx prefix hash: 679ddd64f5a5d65fd05a1f625065a0944b96b61e32e858b19c75eeb0a0302f08
Tx public key: 28d6a5a78d3de3032877d314593c7bcd625339747e42ecc2bb07d6fedc5bd58e
Timestamp: 1718370324 Timestamp [UCT]: 2024-06-14 13:05:24 Age [y:d:h:m:s]: 00:300:19:44:31
Block: 1044050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214974 RingCT/type: yes/0
Extra: 0128d6a5a78d3de3032877d314593c7bcd625339747e42ecc2bb07d6fedc5bd58e02110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d2f45720068d137903517c13c1b8866d95d0d592141d8cb59fd887e74d6ba0c1 0.600000000000 1513251 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": 1044060, "vin": [ { "gen": { "height": 1044050 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2f45720068d137903517c13c1b8866d95d0d592141d8cb59fd887e74d6ba0c1" } } ], "extra": [ 1, 40, 214, 165, 167, 141, 61, 227, 3, 40, 119, 211, 20, 89, 60, 123, 205, 98, 83, 57, 116, 126, 66, 236, 194, 187, 7, 214, 254, 220, 91, 213, 142, 2, 17, 0, 0, 0, 9, 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