Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b333fa65f6573d8175474eeb32c146b5b40082519f5c2b217dd9ed38b4c00daa

Tx prefix hash: 0b9574750e39d13f715c9f0185f156649381f1b4fa8a9f1ec9c508a35a93ec88
Tx public key: 0f2b9f0ba63b6fc51d4ee5512ccc91202042b7d70fd287b99997d29235a25778
Timestamp: 1725819360 Timestamp [UCT]: 2024-09-08 18:16:00 Age [y:d:h:m:s]: 01:059:23:02:04
Block: 1105801 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301272 RingCT/type: yes/0
Extra: 010f2b9f0ba63b6fc51d4ee5512ccc91202042b7d70fd287b99997d29235a2577802110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e00521f6c13e9e0240d8989d69d7755c648743488f0e2fd83ffd32a8da40e3f4 0.600000000000 1583266 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": 1105811, "vin": [ { "gen": { "height": 1105801 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e00521f6c13e9e0240d8989d69d7755c648743488f0e2fd83ffd32a8da40e3f4" } } ], "extra": [ 1, 15, 43, 159, 11, 166, 59, 111, 197, 29, 78, 229, 81, 44, 204, 145, 32, 32, 66, 183, 215, 15, 210, 135, 185, 153, 151, 210, 146, 53, 162, 87, 120, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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