Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: beeea02102205aed81922b3d07f6dff9543b5bca4b9736f8375111200a971b04

Tx prefix hash: cf3f9a25209c3aea9dab7938ba3b370ca2295584538f09e8e673386a022e9c05
Tx public key: b0c39fc6d0c40eb1a98cabfa33ca00bcac2758c4044f9ad130925dc46f8daa2c
Timestamp: 1644321773 Timestamp [UCT]: 2022-02-08 12:02:53 Age [y:d:h:m:s]: 02:271:00:42:49
Block: 434439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 712649 RingCT/type: yes/0
Extra: 01b0c39fc6d0c40eb1a98cabfa33ca00bcac2758c4044f9ad130925dc46f8daa2c021100000009c9067537000000000000000000

1 output(s) for total of 22.311231907000 dcy

stealth address amount amount idx
00: f180f94c345b5392961145abdd7dfc15f74bb51cc80b4bcc7d2c9e9d144ede7a 22.311231907000 845380 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": 434449, "vin": [ { "gen": { "height": 434439 } } ], "vout": [ { "amount": 22311231907, "target": { "key": "f180f94c345b5392961145abdd7dfc15f74bb51cc80b4bcc7d2c9e9d144ede7a" } } ], "extra": [ 1, 176, 195, 159, 198, 208, 196, 14, 177, 169, 140, 171, 250, 51, 202, 0, 188, 172, 39, 88, 196, 4, 79, 154, 209, 48, 146, 93, 196, 111, 141, 170, 44, 2, 17, 0, 0, 0, 9, 201, 6, 117, 55, 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