Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6658be27c81c78b74d5cef8fb195821dd03889528eb683ba1c1ff4a61d902c4f

Tx prefix hash: 34178319ac75bbfe21d7f2023a9d5d9c014e8b559748268e5ddc54523ddde7c0
Tx public key: c3fbfa5faae8de0dbb781d6bbc04ce5f415ddbd0fbb236637b05ce4829e8c356
Timestamp: 1753514191 Timestamp [UCT]: 2025-07-26 07:16:31 Age [y:d:h:m:s]: 00:118:11:10:09
Block: 1333630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83498 RingCT/type: yes/0
Extra: 01c3fbfa5faae8de0dbb781d6bbc04ce5f415ddbd0fbb236637b05ce4829e8c35602110000000bef221485000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12c2582c82df68e93a0ae39e8e4e07ff8a381732324430155c2a286ad22d1838 0.600000000000 1821429 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": 1333640, "vin": [ { "gen": { "height": 1333630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12c2582c82df68e93a0ae39e8e4e07ff8a381732324430155c2a286ad22d1838" } } ], "extra": [ 1, 195, 251, 250, 95, 170, 232, 222, 13, 187, 120, 29, 107, 188, 4, 206, 95, 65, 93, 219, 208, 251, 178, 54, 99, 123, 5, 206, 72, 41, 232, 195, 86, 2, 17, 0, 0, 0, 11, 239, 34, 20, 133, 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