Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cc26b6c6284216d21fd661524eb8e7ef92f326733e9d8b9a374ef7e35ee5897

Tx prefix hash: c972c05ce41778a714a696e5f5fcf9806a3bf30afdf8f8e34887d49e6bb9f513
Tx public key: c7f5647e21b0e177d14ed45b45f91a8d96a88364999e17e5cbdba64caa149ca7
Timestamp: 1755090928 Timestamp [UCT]: 2025-08-13 13:15:28 Age [y:d:h:m:s]: 00:068:06:28:17
Block: 1346078 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48204 RingCT/type: yes/0
Extra: 01c7f5647e21b0e177d14ed45b45f91a8d96a88364999e17e5cbdba64caa149ca7021100000006b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38dd6d57f3357914a20f7505ceb367f4553309e4e368fc8e9775d890fb942720 0.600000000000 1833975 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": 1346088, "vin": [ { "gen": { "height": 1346078 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38dd6d57f3357914a20f7505ceb367f4553309e4e368fc8e9775d890fb942720" } } ], "extra": [ 1, 199, 245, 100, 126, 33, 176, 225, 119, 209, 78, 212, 91, 69, 249, 26, 141, 150, 168, 131, 100, 153, 158, 23, 229, 203, 219, 166, 76, 170, 20, 156, 167, 2, 17, 0, 0, 0, 6, 178, 247, 132, 196, 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