Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 787a38696c7dea445d6ec72197b3fe665e73ce1abfaecad5105b36cad318d88a

Tx prefix hash: 11493d67febd5d8bd9fc21fbeff82178a24a199df72b379e34f7a322daf43620
Tx public key: c43109cb221e7505e392aea3f762096ef61e5e1ed5ed7d0220056d82aa65cb0e
Timestamp: 1731828491 Timestamp [UCT]: 2024-11-17 07:28:11 Age [y:d:h:m:s]: 00:348:02:26:07
Block: 1155518 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246337 RingCT/type: yes/0
Extra: 01c43109cb221e7505e392aea3f762096ef61e5e1ed5ed7d0220056d82aa65cb0e021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c86f70b6dd957fa8b7292756ddcf9c9aa473727d83aacdff3f1f054c792d7508 0.600000000000 1641135 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": 1155528, "vin": [ { "gen": { "height": 1155518 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c86f70b6dd957fa8b7292756ddcf9c9aa473727d83aacdff3f1f054c792d7508" } } ], "extra": [ 1, 196, 49, 9, 203, 34, 30, 117, 5, 227, 146, 174, 163, 247, 98, 9, 110, 246, 30, 94, 30, 213, 237, 125, 2, 32, 5, 109, 130, 170, 101, 203, 14, 2, 17, 0, 0, 0, 2, 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