Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d95a6a7a22d3cc3284dade021534640687db487879dda0ce25be7c2ce7811129

Tx prefix hash: 22864c273d205bae4d635d11b0cff933b6b9aea3a9a03971fba5861903127739
Tx public key: 487b1d3076ffdb54d8ccb43fb1d2cfb123c8de624aa3a824d7cc52e68d8f4b3b
Timestamp: 1707983928 Timestamp [UCT]: 2024-02-15 07:58:48 Age [y:d:h:m:s]: 01:042:09:29:07
Block: 957931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291339 RingCT/type: yes/0
Extra: 01487b1d3076ffdb54d8ccb43fb1d2cfb123c8de624aa3a824d7cc52e68d8f4b3b0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8b964958ec309cd0ced588128e6b356cd4da87f947cdc020531cf2ed59ea60e 0.600000000000 1417282 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": 957941, "vin": [ { "gen": { "height": 957931 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8b964958ec309cd0ced588128e6b356cd4da87f947cdc020531cf2ed59ea60e" } } ], "extra": [ 1, 72, 123, 29, 48, 118, 255, 219, 84, 216, 204, 180, 63, 177, 210, 207, 177, 35, 200, 222, 98, 74, 163, 168, 36, 215, 204, 82, 230, 141, 143, 75, 59, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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