Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c592f675882487020b0b9e18cf3726c6c2e49f59c7b20438b94e75a1f3f73a1

Tx prefix hash: c1ee6318d82f0738befd0b64bae46acb3b982e8f533e34b1c092e2915ba670ca
Tx public key: 464b4127618de06b8da00b6b2719efb80d846202c99345f130011ae9f1119ff9
Timestamp: 1708099030 Timestamp [UCT]: 2024-02-16 15:57:10 Age [y:d:h:m:s]: 00:347:08:11:03
Block: 958888 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248390 RingCT/type: yes/0
Extra: 01464b4127618de06b8da00b6b2719efb80d846202c99345f130011ae9f1119ff902110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a96e9c3a8fc8906392bb586a310e9fb00defa564e797e8750f69911e239c0ceb 0.600000000000 1418315 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": 958898, "vin": [ { "gen": { "height": 958888 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a96e9c3a8fc8906392bb586a310e9fb00defa564e797e8750f69911e239c0ceb" } } ], "extra": [ 1, 70, 75, 65, 39, 97, 141, 224, 107, 141, 160, 11, 107, 39, 25, 239, 184, 13, 132, 98, 2, 201, 147, 69, 241, 48, 1, 26, 233, 241, 17, 159, 249, 2, 17, 0, 0, 0, 2, 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