Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c96a88a47d9c7d3b14ce65be02aa38e4a9f721bc225bfae4e9d18334a20c7a90

Tx prefix hash: 06577c5f655dacd54b85a9ffb4cc03454560e338c9c4cadbfae1311dfe922d1c
Tx public key: 435b9e2cd666ec18611c760ac6921b5454af501abd28294034d4bfb34bf65504
Timestamp: 1723853620 Timestamp [UCT]: 2024-08-17 00:13:40 Age [y:d:h:m:s]: 00:231:02:40:25
Block: 1089510 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165038 RingCT/type: yes/0
Extra: 01435b9e2cd666ec18611c760ac6921b5454af501abd28294034d4bfb34bf65504021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76c2af0db37d741f4c224fe96dd1d45e0e6e42e3d8e33b5bb5f0bbfdfa5f89db 0.600000000000 1564131 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": 1089520, "vin": [ { "gen": { "height": 1089510 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76c2af0db37d741f4c224fe96dd1d45e0e6e42e3d8e33b5bb5f0bbfdfa5f89db" } } ], "extra": [ 1, 67, 91, 158, 44, 214, 102, 236, 24, 97, 28, 118, 10, 198, 146, 27, 84, 84, 175, 80, 26, 189, 40, 41, 64, 52, 212, 191, 179, 75, 246, 85, 4, 2, 17, 0, 0, 0, 2, 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