Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c39087f89616b8ffe9c53a408ef55b6fdd95288cbb2ce3200381ef4e3251669

Tx prefix hash: d9f2a7b794c39927173633fbda7a371bda924deb22b4f26aab36f809c2656c3c
Tx public key: e8c6d9262fdb028db06c5552413ee1dc0e5bb4818fb27dad6cf4eaedf0697f0d
Timestamp: 1728457907 Timestamp [UCT]: 2024-10-09 07:11:47 Age [y:d:h:m:s]: 00:107:17:59:13
Block: 1127673 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76994 RingCT/type: yes/0
Extra: 01e8c6d9262fdb028db06c5552413ee1dc0e5bb4818fb27dad6cf4eaedf0697f0d02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03648dd1c3a398415305d4140dd3f04913f522cfcfd84238b4576a93ce029b8d 0.600000000000 1610480 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": 1127683, "vin": [ { "gen": { "height": 1127673 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03648dd1c3a398415305d4140dd3f04913f522cfcfd84238b4576a93ce029b8d" } } ], "extra": [ 1, 232, 198, 217, 38, 47, 219, 2, 141, 176, 108, 85, 82, 65, 62, 225, 220, 14, 91, 180, 129, 143, 178, 125, 173, 108, 244, 234, 237, 240, 105, 127, 13, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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