Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11e8e3ac52479b4d1c20c6e1f2acb2910e3d29505788ccc9cbe74ea2cc9cc25b

Tx prefix hash: 9dffe485ade31a1dfe7c166c805a6cfa1352fe25b9aaf427b64004fc517898af
Tx public key: f4cec0177bb72835f540a1b194c03cb2a8ca0b9220f05cc97a70a1db184a6825
Timestamp: 1736513079 Timestamp [UCT]: 2025-01-10 12:44:39 Age [y:d:h:m:s]: 00:067:22:55:28
Block: 1194314 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48362 RingCT/type: yes/0
Extra: 01f4cec0177bb72835f540a1b194c03cb2a8ca0b9220f05cc97a70a1db184a68250211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f9a2bfa8fb73ade4cbb8807bcb58184a7cf3cb2a5c346aea4459582e6e0f37e 0.600000000000 1680883 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": 1194324, "vin": [ { "gen": { "height": 1194314 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f9a2bfa8fb73ade4cbb8807bcb58184a7cf3cb2a5c346aea4459582e6e0f37e" } } ], "extra": [ 1, 244, 206, 192, 23, 123, 183, 40, 53, 245, 64, 161, 177, 148, 192, 60, 178, 168, 202, 11, 146, 32, 240, 92, 201, 122, 112, 161, 219, 24, 74, 104, 37, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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