Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15521ba5fe47e61789211cdda64a0d3630e9a5a65fdb317098538693e291536d

Tx prefix hash: b60dd54b6657b03517b3ccd7d1d6a7923c71b65c6476c03dfd8cf968d2746545
Tx public key: a22c374ff50580906fe4da8d4ea119a6b33dad8c4ebe13ddd7662a6d4aaeac58
Timestamp: 1581820528 Timestamp [UCT]: 2020-02-16 02:35:28 Age [y:d:h:m:s]: 04:321:16:59:35
Block: 65716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1122365 RingCT/type: yes/0
Extra: 01a22c374ff50580906fe4da8d4ea119a6b33dad8c4ebe13ddd7662a6d4aaeac5802110000000156c366d3000000000000000000

1 output(s) for total of 371.754660661000 dcy

stealth address amount amount idx
00: ec8aa2539002bc016202126cd57b6c6a4e40d844904ada3eb5612d8c74738d61 371.754660661000 121283 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": 65726, "vin": [ { "gen": { "height": 65716 } } ], "vout": [ { "amount": 371754660661, "target": { "key": "ec8aa2539002bc016202126cd57b6c6a4e40d844904ada3eb5612d8c74738d61" } } ], "extra": [ 1, 162, 44, 55, 79, 245, 5, 128, 144, 111, 228, 218, 141, 78, 161, 25, 166, 179, 61, 173, 140, 78, 190, 19, 221, 215, 102, 42, 109, 74, 174, 172, 88, 2, 17, 0, 0, 0, 1, 86, 195, 102, 211, 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