Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8660028a71d18dcbb78a9354354ac6ae18d1c2299be2f69167a0e0da567ca3a

Tx prefix hash: c72f8cf9840cac656b63fa08239ecdd5f4be01d84b1b3b63d8106252e268698b
Tx public key: c4a4ec31d30f61c84764b1f352ba03d297fce6cfb076e931fffb523325b40e7d
Timestamp: 1696264741 Timestamp [UCT]: 2023-10-02 16:39:01 Age [y:d:h:m:s]: 01:187:02:22:42
Block: 860984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394755 RingCT/type: yes/0
Extra: 01c4a4ec31d30f61c84764b1f352ba03d297fce6cfb076e931fffb523325b40e7d02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.861395576000 dcy

stealth address amount amount idx
00: 1a0a1db63fa631a8197a1d10a2ca913f0bd942db72fc099f1a0dccb3522b96df 0.861395576000 1315294 of 0

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": 860994, "vin": [ { "gen": { "height": 860984 } } ], "vout": [ { "amount": 861395576, "target": { "key": "1a0a1db63fa631a8197a1d10a2ca913f0bd942db72fc099f1a0dccb3522b96df" } } ], "extra": [ 1, 196, 164, 236, 49, 211, 15, 97, 200, 71, 100, 177, 243, 82, 186, 3, 210, 151, 252, 230, 207, 176, 118, 233, 49, 255, 251, 82, 51, 37, 180, 14, 125, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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