Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 692299e9914869ea21a66c39a8f061f3331d9318ea10650caf39f4c83f897d2f

Tx prefix hash: cecb24141447d6d6a7da8bb659e16bae8483464aa6e0ce143e367267e8b5aa20
Tx public key: 0341dc195aac37f2c5a09b9a4bb973bf664d117792cdd1bf3e3417d389fc4466
Timestamp: 1743125579 Timestamp [UCT]: 2025-03-28 01:32:59 Age [y:d:h:m:s]: 00:311:13:35:06
Block: 1248791 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220339 RingCT/type: yes/0
Extra: 010341dc195aac37f2c5a09b9a4bb973bf664d117792cdd1bf3e3417d389fc4466021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63f73f4d1a0d45a43859197d043d639f7e432b0a11ab409e825f75a095f93dbd 0.600000000000 1735826 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": 1248801, "vin": [ { "gen": { "height": 1248791 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63f73f4d1a0d45a43859197d043d639f7e432b0a11ab409e825f75a095f93dbd" } } ], "extra": [ 1, 3, 65, 220, 25, 90, 172, 55, 242, 197, 160, 155, 154, 75, 185, 115, 191, 102, 77, 17, 119, 146, 205, 209, 191, 62, 52, 23, 211, 137, 252, 68, 102, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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