Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f051a13707685496da8a59e199cd2d979da2cb24061a98bc7920b8a24258f96f

Tx prefix hash: 6804b8ba6c02706e8709adeff9a8e47a9083d4fe0a5f896112f0811f3a9adcc2
Tx public key: f2791e4deddb983522ec86ae5ffdabb7a05f319b511a570eaaf9be40b5455b29
Timestamp: 1718784078 Timestamp [UCT]: 2024-06-19 08:01:18 Age [y:d:h:m:s]: 00:166:00:08:57
Block: 1047481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118807 RingCT/type: yes/0
Extra: 01f2791e4deddb983522ec86ae5ffdabb7a05f319b511a570eaaf9be40b5455b290211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae843081e6b39573827894247146d1172f706d17c67c0b8d3ca338a5fc09cbb8 0.600000000000 1517316 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": 1047491, "vin": [ { "gen": { "height": 1047481 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae843081e6b39573827894247146d1172f706d17c67c0b8d3ca338a5fc09cbb8" } } ], "extra": [ 1, 242, 121, 30, 77, 237, 219, 152, 53, 34, 236, 134, 174, 95, 253, 171, 183, 160, 95, 49, 155, 81, 26, 87, 14, 170, 249, 190, 64, 181, 69, 91, 41, 2, 17, 0, 0, 0, 5, 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