Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02c9c456b71da223bb01f4b9d027d59e9c206d12a2c98e38a15d61aa85cbdf54

Tx prefix hash: 5d3ccf0e635fbf70712d88f365ec7817444a74ebc7f97515ed625d9288dd42b0
Tx public key: d2d453efe5acf8fe871113e81197aa77c12d0bd523f867c1bdb221028d794b47
Timestamp: 1731203504 Timestamp [UCT]: 2024-11-10 01:51:44 Age [y:d:h:m:s]: 00:127:09:25:15
Block: 1150360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90878 RingCT/type: yes/0
Extra: 01d2d453efe5acf8fe871113e81197aa77c12d0bd523f867c1bdb221028d794b47021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8a0ca0555e7d8e13ea9f0139311e5f550fc4668bd6a62cb971c5774154acf98 0.600000000000 1635649 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": 1150370, "vin": [ { "gen": { "height": 1150360 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8a0ca0555e7d8e13ea9f0139311e5f550fc4668bd6a62cb971c5774154acf98" } } ], "extra": [ 1, 210, 212, 83, 239, 229, 172, 248, 254, 135, 17, 19, 232, 17, 151, 170, 119, 193, 45, 11, 213, 35, 248, 103, 193, 189, 178, 33, 2, 141, 121, 75, 71, 2, 17, 0, 0, 0, 2, 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