Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eebe88edebc98b8dbf33a6ad91629bc4b39698cd2a9e0d282448168beae2af14

Tx prefix hash: d83bf876daa9129219cd931c56d03f79c6d9cbd3d1023efa40eed55292b30ce5
Tx public key: df2a359f2bac39ef14c89d611be5a76c55086adcb01fbcc1626f10c935a85c2c
Timestamp: 1702232176 Timestamp [UCT]: 2023-12-10 18:16:16 Age [y:d:h:m:s]: 01:127:17:31:27
Block: 910251 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352438 RingCT/type: yes/0
Extra: 01df2a359f2bac39ef14c89d611be5a76c55086adcb01fbcc1626f10c935a85c2c021100000009e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43a4d0d79300d0093f9bfc7a344bc8e0bba962f940bd992057a455d870a64778 0.600000000000 1367396 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": 910261, "vin": [ { "gen": { "height": 910251 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43a4d0d79300d0093f9bfc7a344bc8e0bba962f940bd992057a455d870a64778" } } ], "extra": [ 1, 223, 42, 53, 159, 43, 172, 57, 239, 20, 200, 157, 97, 27, 229, 167, 108, 85, 8, 106, 220, 176, 31, 188, 193, 98, 111, 16, 201, 53, 168, 92, 44, 2, 17, 0, 0, 0, 9, 230, 210, 127, 156, 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