Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bb36ab0d522c01cea0772a42bb96815cb4301e8246a0d336f6b867193992824

Tx prefix hash: 50aefa479c2a983937b673ec0932e6b866b2299f870440ee3da2874d7050c367
Tx public key: 302c198e9a3aa3e7071dca025354083b34bdde7baf3fa5acc45b21f0d2c77934
Timestamp: 1712097258 Timestamp [UCT]: 2024-04-02 22:34:18 Age [y:d:h:m:s]: 01:013:02:00:18
Block: 992006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270340 RingCT/type: yes/0
Extra: 01302c198e9a3aa3e7071dca025354083b34bdde7baf3fa5acc45b21f0d2c7793402110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7921b1f1e0b203a2df8fd7f4073e14318138258cce3107f3d8b4a34460ff73a3 0.600000000000 1452342 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": 992016, "vin": [ { "gen": { "height": 992006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7921b1f1e0b203a2df8fd7f4073e14318138258cce3107f3d8b4a34460ff73a3" } } ], "extra": [ 1, 48, 44, 25, 142, 154, 58, 163, 231, 7, 29, 202, 2, 83, 84, 8, 59, 52, 189, 222, 123, 175, 63, 165, 172, 196, 91, 33, 240, 210, 199, 121, 52, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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