Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3ddf47f87e5203dfba204ba1634e4564f0164402615c18213bd382192dd24d1

Tx prefix hash: b9e375af0e9fea9756f6c2024ed77f4406ce100d7f89dc3576622b30671156d7
Tx public key: a9c9307cd886c3d0985aeac31b4b6043e9576ed0e7f3d81c5bb02715f70c6260
Timestamp: 1735860296 Timestamp [UCT]: 2025-01-02 23:24:56 Age [y:d:h:m:s]: 00:166:01:55:02
Block: 1188913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118413 RingCT/type: yes/0
Extra: 01a9c9307cd886c3d0985aeac31b4b6043e9576ed0e7f3d81c5bb02715f70c6260021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0793a265b43d2f6a3aa52ebdfa7aab9989dc6dbb78d7aa96d617654fdb621e86 0.600000000000 1675418 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": 1188923, "vin": [ { "gen": { "height": 1188913 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0793a265b43d2f6a3aa52ebdfa7aab9989dc6dbb78d7aa96d617654fdb621e86" } } ], "extra": [ 1, 169, 201, 48, 124, 216, 134, 195, 208, 152, 90, 234, 195, 27, 75, 96, 67, 233, 87, 110, 208, 231, 243, 216, 28, 91, 176, 39, 21, 247, 12, 98, 96, 2, 17, 0, 0, 0, 6, 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