Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9af6ed24c94eea3ccd47eed26ba918b6be821069a967b7d75c73f7c040a3420d

Tx prefix hash: e3423758888408e84a94f7013f4d6b4f200ee5c9948a69140a7874f1df7beb57
Tx public key: 67dc7931f4cf2d36c9e974cca8e675f3ed630152354b4ea04011927fbd4873d0
Timestamp: 1713912171 Timestamp [UCT]: 2024-04-23 22:42:51 Age [y:d:h:m:s]: 00:345:20:17:46
Block: 1007083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247233 RingCT/type: yes/0
Extra: 0167dc7931f4cf2d36c9e974cca8e675f3ed630152354b4ea04011927fbd4873d00211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 88a95ab6c67c02f054d85671b0d798330caf06a7c92181283bc872eacf964844 0.600000000000 1468313 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": 1007093, "vin": [ { "gen": { "height": 1007083 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88a95ab6c67c02f054d85671b0d798330caf06a7c92181283bc872eacf964844" } } ], "extra": [ 1, 103, 220, 121, 49, 244, 207, 45, 54, 201, 233, 116, 204, 168, 230, 117, 243, 237, 99, 1, 82, 53, 75, 78, 160, 64, 17, 146, 127, 189, 72, 115, 208, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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