Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9889a0686f8d2ed94769d5c358572f4023accf1085ab526c2f55dc9e196d8d32

Tx prefix hash: 274b0436881059d2935ab8fa71938bdef37cdde3b6731c8530c6ae9658c0f396
Tx public key: 00daf25994189af0369acb4f0f5139120e2ea8e8863d277d45d04cebcc14fa51
Timestamp: 1699332461 Timestamp [UCT]: 2023-11-07 04:47:41 Age [y:d:h:m:s]: 01:194:20:09:01
Block: 886217 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 400474 RingCT/type: yes/0
Extra: 0100daf25994189af0369acb4f0f5139120e2ea8e8863d277d45d04cebcc14fa5102110000000175e3f0e9000000000000000000

1 output(s) for total of 0.710550904000 dcy

stealth address amount amount idx
00: 91b696fedd46e59405e8d9f59f30cc3f9631322d1509a2467a468c0e8152d1af 0.710550904000 1342026 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": 886227, "vin": [ { "gen": { "height": 886217 } } ], "vout": [ { "amount": 710550904, "target": { "key": "91b696fedd46e59405e8d9f59f30cc3f9631322d1509a2467a468c0e8152d1af" } } ], "extra": [ 1, 0, 218, 242, 89, 148, 24, 154, 240, 54, 154, 203, 79, 15, 81, 57, 18, 14, 46, 168, 232, 134, 61, 39, 125, 69, 208, 76, 235, 204, 20, 250, 81, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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