Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e8ea264406b974a952fc915d98898a2458329d1a8aa31fb6ac2fbfebffb46ae

Tx prefix hash: 11aa2b3507360e3acf98477b8f58ddc9953625252bb907915db8e7427d749843
Tx public key: d0350cdc9de9bd7ade8cfd96406c90f37c06ec1fc1d4e66ed4556f6a00e59073
Timestamp: 1733417874 Timestamp [UCT]: 2024-12-05 16:57:54 Age [y:d:h:m:s]: 00:192:08:34:44
Block: 1168695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137222 RingCT/type: yes/0
Extra: 01d0350cdc9de9bd7ade8cfd96406c90f37c06ec1fc1d4e66ed4556f6a00e59073021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5d4b447b02f0bc25f9f380f7665588f627f96c3e8dc8f29ba8af865d5d68984 0.600000000000 1654406 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": 1168705, "vin": [ { "gen": { "height": 1168695 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5d4b447b02f0bc25f9f380f7665588f627f96c3e8dc8f29ba8af865d5d68984" } } ], "extra": [ 1, 208, 53, 12, 220, 157, 233, 189, 122, 222, 140, 253, 150, 64, 108, 144, 243, 124, 6, 236, 31, 193, 212, 230, 110, 212, 85, 111, 106, 0, 229, 144, 115, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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