Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e541c218bcd2bdfe9825bf38bd3438260aa9543bc3de71455bd53f619a79346

Tx prefix hash: 27a3e6c262b49594923fe6f906b84b3fce2c62054a9352f20cd30e62b6278225
Tx public key: c9b6e13af1bf1757962409ca442aa29dd4c8676be8b4e64beb4d46b89ba18c7d
Timestamp: 1696936370 Timestamp [UCT]: 2023-10-10 11:12:50 Age [y:d:h:m:s]: 01:187:11:11:46
Block: 866556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395009 RingCT/type: yes/0
Extra: 01c9b6e13af1bf1757962409ca442aa29dd4c8676be8b4e64beb4d46b89ba18c7d021100000001faf35c9c000000000000000000

1 output(s) for total of 0.825544104000 dcy

stealth address amount amount idx
00: b7684e3774055cb31858d15781e3a947cd925bb7960716721913d5db354ed456 0.825544104000 1321162 of 0

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": 866566, "vin": [ { "gen": { "height": 866556 } } ], "vout": [ { "amount": 825544104, "target": { "key": "b7684e3774055cb31858d15781e3a947cd925bb7960716721913d5db354ed456" } } ], "extra": [ 1, 201, 182, 225, 58, 241, 191, 23, 87, 150, 36, 9, 202, 68, 42, 162, 157, 212, 200, 103, 107, 232, 180, 230, 75, 235, 77, 70, 184, 155, 161, 140, 125, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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