Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1ac8a49e234a9ec4037a64ba12b77bdcbe2d59f2a77752222f1edd421bebd16

Tx prefix hash: 528ac5bc37840445ce951b8d0ccf0bceb4ec6f5676b9c6531d35fd299621e925
Tx public key: 45a3a6cb9f648237ab845a90e4f8f3b610f1dc3b4ff862eebc6f08369aa8bbcb
Timestamp: 1736379888 Timestamp [UCT]: 2025-01-08 23:44:48 Age [y:d:h:m:s]: 00:343:02:06:13
Block: 1193218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242753 RingCT/type: yes/0
Extra: 0145a3a6cb9f648237ab845a90e4f8f3b610f1dc3b4ff862eebc6f08369aa8bbcb021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 88ba9823628eb3d057a27624905d69e039e2326c8877dfccbe4960176e025c5c 0.600000000000 1679777 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": 1193228, "vin": [ { "gen": { "height": 1193218 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88ba9823628eb3d057a27624905d69e039e2326c8877dfccbe4960176e025c5c" } } ], "extra": [ 1, 69, 163, 166, 203, 159, 100, 130, 55, 171, 132, 90, 144, 228, 248, 243, 182, 16, 241, 220, 59, 79, 248, 98, 238, 188, 111, 8, 54, 154, 168, 187, 203, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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