Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 738e657d42cb5839d2a624dc82b54e254748a2c96c57162f7acdc14d162c1b17

Tx prefix hash: 3fc7dafc7b44187b0ee5c7fcc1d2a5eae3d26fe6d8b5941d6a99ed6b96e5972e
Tx public key: 7714a74af441dcd533d896b4f015cfd9c8d9d218d9545357d25eb10d1216950d
Timestamp: 1674060654 Timestamp [UCT]: 2023-01-18 16:50:54 Age [y:d:h:m:s]: 02:115:21:35:26
Block: 677556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 604520 RingCT/type: yes/0
Extra: 017714a74af441dcd533d896b4f015cfd9c8d9d218d9545357d25eb10d1216950d021100000001faf35c9c000000000000000000

1 output(s) for total of 3.491207415000 dcy

stealth address amount amount idx
00: 02a32c5dff3a63ee767d28f44c6a5d10d17600464c36eb46d015427557be4703 3.491207415000 1119339 of 0

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": 677566, "vin": [ { "gen": { "height": 677556 } } ], "vout": [ { "amount": 3491207415, "target": { "key": "02a32c5dff3a63ee767d28f44c6a5d10d17600464c36eb46d015427557be4703" } } ], "extra": [ 1, 119, 20, 167, 74, 244, 65, 220, 213, 51, 216, 150, 180, 240, 21, 207, 217, 200, 217, 210, 24, 217, 84, 83, 87, 210, 94, 177, 13, 18, 22, 149, 13, 2, 17, 0, 0, 0, 1, 250, 243, 92, 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