Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0f4631e97fed2fbe27b81869f4d301ee07f68dda38bd93e356b3556b375f920

Tx prefix hash: d69df09768a2054123d22c92b3310104adaf36a0352823c7ee04825e8771d172
Tx public key: d80bec454adc5c7f43fc96acac37a7c2fb5ed886dbe5f9e0ec1d9e2c910b826c
Timestamp: 1760729452 Timestamp [UCT]: 2025-10-17 19:30:52 Age [y:d:h:m:s]: 00:067:04:46:29
Block: 1392120 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48094 RingCT/type: yes/0
Extra: 01d80bec454adc5c7f43fc96acac37a7c2fb5ed886dbe5f9e0ec1d9e2c910b826c021100000001df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d30c728ac4cab28fef1ba12b65ac2f98e39abd7ec25a553f662e4a5eaaff2a2b 0.600000000000 1880371 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": 1392130, "vin": [ { "gen": { "height": 1392120 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d30c728ac4cab28fef1ba12b65ac2f98e39abd7ec25a553f662e4a5eaaff2a2b" } } ], "extra": [ 1, 216, 11, 236, 69, 74, 220, 92, 127, 67, 252, 150, 172, 172, 55, 167, 194, 251, 94, 216, 134, 219, 229, 249, 224, 236, 29, 158, 44, 145, 11, 130, 108, 2, 17, 0, 0, 0, 1, 223, 90, 36, 122, 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