Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d9b897d61cac219e2af6613b59eb7003d1b2fc651099e5f31ba647bd715a03f

Tx prefix hash: e7b9eb175f4120328f6d15fd733244e1e78d06942c0f072fcbff4993e700e737
Tx public key: f1f8ecf4f7698422e428bfd31269148c143b3ef054155ac4c1d6da1bde14e727
Timestamp: 1718648423 Timestamp [UCT]: 2024-06-17 18:20:23 Age [y:d:h:m:s]: 00:294:07:10:24
Block: 1046350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210292 RingCT/type: yes/0
Extra: 01f1f8ecf4f7698422e428bfd31269148c143b3ef054155ac4c1d6da1bde14e72702110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ece4568e4daef8855ec5664d8de7ee98cfb2bea3afd53ba97192cbb022e6373 0.600000000000 1516161 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": 1046360, "vin": [ { "gen": { "height": 1046350 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ece4568e4daef8855ec5664d8de7ee98cfb2bea3afd53ba97192cbb022e6373" } } ], "extra": [ 1, 241, 248, 236, 244, 247, 105, 132, 34, 228, 40, 191, 211, 18, 105, 20, 140, 20, 59, 62, 240, 84, 21, 90, 196, 193, 214, 218, 27, 222, 20, 231, 39, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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