Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3367922d1433be475c3a8cd25741486523cc54f479d9a2e37c1389f93ae38dab

Tx prefix hash: 4ca97bdd46d9a152262aae023a7d3a2e1735a4cdf2cc809398f4a6876410c9f1
Tx public key: 0c766538054891c8b4386f67d3db808c6efad304f14d1d6e97421bcefe001d65
Timestamp: 1709158709 Timestamp [UCT]: 2024-02-28 22:18:29 Age [y:d:h:m:s]: 01:253:14:04:21
Block: 967682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439957 RingCT/type: yes/0
Extra: 010c766538054891c8b4386f67d3db808c6efad304f14d1d6e97421bcefe001d650211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 915f0fc1d614af9a646efe432f42d6e308a916299feb6cea7b71d4d3c715a858 0.600000000000 1427465 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": 967692, "vin": [ { "gen": { "height": 967682 } } ], "vout": [ { "amount": 600000000, "target": { "key": "915f0fc1d614af9a646efe432f42d6e308a916299feb6cea7b71d4d3c715a858" } } ], "extra": [ 1, 12, 118, 101, 56, 5, 72, 145, 200, 180, 56, 111, 103, 211, 219, 128, 140, 110, 250, 211, 4, 241, 77, 29, 110, 151, 66, 27, 206, 254, 0, 29, 101, 2, 17, 0, 0, 0, 3, 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