Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7766719dea59df58f92ed299707a9e640574da86280efae9966d2733398902a

Tx prefix hash: 8ffac9bc7f0c8df73e88b10bdb10f29393abb4db4a67e8dce1e47b24c340df57
Tx public key: 4031b12cde357f8735a8c3d5e3a676474c2ee0ec8e3c8c3d9f373e39f04e45ac
Timestamp: 1699619511 Timestamp [UCT]: 2023-11-10 12:31:51 Age [y:d:h:m:s]: 01:130:18:24:49
Block: 888597 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354651 RingCT/type: yes/0
Extra: 014031b12cde357f8735a8c3d5e3a676474c2ee0ec8e3c8c3d9f373e39f04e45ac021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.697765134000 dcy

stealth address amount amount idx
00: e32d62712e5d1635c30db02ee16c61b6af8e562c9bacca9e1f9e172cd40cede4 0.697765134000 1344544 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": 888607, "vin": [ { "gen": { "height": 888597 } } ], "vout": [ { "amount": 697765134, "target": { "key": "e32d62712e5d1635c30db02ee16c61b6af8e562c9bacca9e1f9e172cd40cede4" } } ], "extra": [ 1, 64, 49, 177, 44, 222, 53, 127, 135, 53, 168, 195, 213, 227, 166, 118, 71, 76, 46, 224, 236, 142, 60, 140, 61, 159, 55, 62, 57, 240, 78, 69, 172, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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