Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e454d8a5bbab539e6cc08aea1b3470c4b721f9a9760b19dfbab83488166af631

Tx prefix hash: b3b3fc7c388a72d8e0bc5a4c6cd5ff38cf04b614856849198d11b7b050f18f72
Tx public key: ee266eb5fd7853cb00bf4315ff98ffe6b5e8e1c37635182826d2b38133458196
Timestamp: 1718943518 Timestamp [UCT]: 2024-06-21 04:18:38 Age [y:d:h:m:s]: 00:278:06:54:03
Block: 1048814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198816 RingCT/type: yes/0
Extra: 01ee266eb5fd7853cb00bf4315ff98ffe6b5e8e1c37635182826d2b381334581960211000000010cce0636000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d68e7ce83e3c7f6a88a6cb08e38416c15bb511f2bcc34cc0dc23ecab83e17c8 0.600000000000 1518901 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": 1048824, "vin": [ { "gen": { "height": 1048814 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d68e7ce83e3c7f6a88a6cb08e38416c15bb511f2bcc34cc0dc23ecab83e17c8" } } ], "extra": [ 1, 238, 38, 110, 181, 253, 120, 83, 203, 0, 191, 67, 21, 255, 152, 255, 230, 181, 232, 225, 195, 118, 53, 24, 40, 38, 210, 179, 129, 51, 69, 129, 150, 2, 17, 0, 0, 0, 1, 12, 206, 6, 54, 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