Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7b5d4c336e6d9be13361a0e2d5933155c7ce492901a4a16a148f2bc3154f931

Tx prefix hash: 5e7c63f6797389e17f8ce54672bbb094002646ff4bb2470c5ddbc0ed5957798e
Tx public key: 8eeca5cdc6c80c9572b295a2efe935666a96be328f6df47ab1e0330795b227f4
Timestamp: 1703541250 Timestamp [UCT]: 2023-12-25 21:54:10 Age [y:d:h:m:s]: 01:100:21:07:59
Block: 921099 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333217 RingCT/type: yes/0
Extra: 018eeca5cdc6c80c9572b295a2efe935666a96be328f6df47ab1e0330795b227f402110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 300c28f9c66692a43606843ae60c2a0d5338762dbc0e636dcef261f3d6171a5b 0.600000000000 1378783 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": 921109, "vin": [ { "gen": { "height": 921099 } } ], "vout": [ { "amount": 600000000, "target": { "key": "300c28f9c66692a43606843ae60c2a0d5338762dbc0e636dcef261f3d6171a5b" } } ], "extra": [ 1, 142, 236, 165, 205, 198, 200, 12, 149, 114, 178, 149, 162, 239, 233, 53, 102, 106, 150, 190, 50, 143, 109, 244, 122, 177, 224, 51, 7, 149, 178, 39, 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