Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 859f74de12ef9162e2c494b9bcce6440f2c56bceaebbed16a3ba75bf3bfea94f

Tx prefix hash: e6f3c47c6b1765581753a931dd295d2bbc7889a9c5550e63819c917e1aeb81df
Tx public key: 38574261e7ecd4980943f7e4d996c872a9ab8b1fa0d74de356c41bb8debf266c
Timestamp: 1710757402 Timestamp [UCT]: 2024-03-18 10:23:22 Age [y:d:h:m:s]: 00:343:08:08:58
Block: 980950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245447 RingCT/type: yes/0
Extra: 0138574261e7ecd4980943f7e4d996c872a9ab8b1fa0d74de356c41bb8debf266c02110000000a52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2d9c16b777f80a5d20f078a28fb30492d50dbc01310c37793a355625ad99291 0.600000000000 1441035 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": 980960, "vin": [ { "gen": { "height": 980950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2d9c16b777f80a5d20f078a28fb30492d50dbc01310c37793a355625ad99291" } } ], "extra": [ 1, 56, 87, 66, 97, 231, 236, 212, 152, 9, 67, 247, 228, 217, 150, 200, 114, 169, 171, 139, 31, 160, 215, 77, 227, 86, 196, 27, 184, 222, 191, 38, 108, 2, 17, 0, 0, 0, 10, 82, 212, 126, 148, 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