Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50d537c77b08da02b5ddb2f698b19d06507f7a08ae98121d9083b88bdbf4e137

Tx prefix hash: ddf7c279da394bde6396e0f4d9184f0690c7491b9c3a3d5a07db316393e22d9c
Tx public key: 893a0cc190b29a8c7acfcfd97900dbffaa5977ee7dc9b929c81979812fa4f479
Timestamp: 1729807822 Timestamp [UCT]: 2024-10-24 22:10:22 Age [y:d:h:m:s]: 00:189:22:12:45
Block: 1138830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135553 RingCT/type: yes/0
Extra: 01893a0cc190b29a8c7acfcfd97900dbffaa5977ee7dc9b929c81979812fa4f479021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82a1b12d9142cf384860983e9b535bdb315f82b8647d2e5e92aa70b4423ae5eb 0.600000000000 1622559 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": 1138840, "vin": [ { "gen": { "height": 1138830 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82a1b12d9142cf384860983e9b535bdb315f82b8647d2e5e92aa70b4423ae5eb" } } ], "extra": [ 1, 137, 58, 12, 193, 144, 178, 154, 140, 122, 207, 207, 217, 121, 0, 219, 255, 170, 89, 119, 238, 125, 201, 185, 41, 200, 25, 121, 129, 47, 164, 244, 121, 2, 17, 0, 0, 0, 4, 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