Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 954c3cbf39d9086ac4dd7657293550382faa9b3ddf8ef8f18e3754185b65afbc

Tx prefix hash: 92f81f8a6dca5495fb6a42d9f7fb5162b5f47f2e23d17ff89b0519d8bd737873
Tx public key: 362ecf5156147d4fb86c5cb5ad40a7888e7acf0a190ffdcce555ad533d7411c4
Timestamp: 1703079908 Timestamp [UCT]: 2023-12-20 13:45:08 Age [y:d:h:m:s]: 01:147:03:23:33
Block: 917285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366304 RingCT/type: yes/0
Extra: 01362ecf5156147d4fb86c5cb5ad40a7888e7acf0a190ffdcce555ad533d7411c4021100000002e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed095acac6f5bd369cedc9297e82849cecdbbb3553f437e7a2bf1cd2ba13a857 0.600000000000 1374855 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": 917295, "vin": [ { "gen": { "height": 917285 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed095acac6f5bd369cedc9297e82849cecdbbb3553f437e7a2bf1cd2ba13a857" } } ], "extra": [ 1, 54, 46, 207, 81, 86, 20, 125, 79, 184, 108, 92, 181, 173, 64, 167, 136, 142, 122, 207, 10, 25, 15, 253, 204, 229, 85, 173, 83, 61, 116, 17, 196, 2, 17, 0, 0, 0, 2, 228, 187, 107, 131, 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