Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b67ac7a33257ced3b43b834c544336bcb73e94d1ee684839e36216aad7f1ffa

Tx prefix hash: 8f41014e6dc193d6f6b0bc9784c3d4b419b0dfd66c9f85e7e4f9d2b0bdb138dd
Tx public key: 8cc53d3d0c3e47ecf4fdc0f60c86507647e1afa9247e376889c945d11d409f91
Timestamp: 1726218867 Timestamp [UCT]: 2024-09-13 09:14:27 Age [y:d:h:m:s]: 00:118:11:48:02
Block: 1109110 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84741 RingCT/type: yes/0
Extra: 018cc53d3d0c3e47ecf4fdc0f60c86507647e1afa9247e376889c945d11d409f91021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7fe14dc2cec92d73af5af2a8fcc4621fdb319875f9ce84ee5a7668c3fe583d8 0.600000000000 1587243 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": 1109120, "vin": [ { "gen": { "height": 1109110 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7fe14dc2cec92d73af5af2a8fcc4621fdb319875f9ce84ee5a7668c3fe583d8" } } ], "extra": [ 1, 140, 197, 61, 61, 12, 62, 71, 236, 244, 253, 192, 246, 12, 134, 80, 118, 71, 225, 175, 169, 36, 126, 55, 104, 137, 201, 69, 209, 29, 64, 159, 145, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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