Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88f4c2f7702247b64ed571f5a08e7a86e9b05030925315ff6ffdfaf4d0433fc4

Tx prefix hash: 57166e5291959f4ec50fd57a70ec0ca897d8abf4653f1d65706693bfaf7a7c1c
Tx public key: fed1bab3f6a9c9f9722265d995a474a515b5ba2dfd565e5f85c5d4a9196055ac
Timestamp: 1713725102 Timestamp [UCT]: 2024-04-21 18:45:02 Age [y:d:h:m:s]: 00:260:20:31:43
Block: 1005529 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186727 RingCT/type: yes/0
Extra: 01fed1bab3f6a9c9f9722265d995a474a515b5ba2dfd565e5f85c5d4a9196055ac0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e87453683d54023efe0b7604b07aceac6499ae79439b1770b3aa484c3b498cb 0.600000000000 1466251 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": 1005539, "vin": [ { "gen": { "height": 1005529 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e87453683d54023efe0b7604b07aceac6499ae79439b1770b3aa484c3b498cb" } } ], "extra": [ 1, 254, 209, 186, 179, 246, 169, 201, 249, 114, 34, 101, 217, 149, 164, 116, 165, 21, 181, 186, 45, 253, 86, 94, 95, 133, 197, 212, 169, 25, 96, 85, 172, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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