Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81476ee4ae232d973d54d2b2f911b803590847aa6f1915d88e41191a29447285

Tx prefix hash: d0731531862fdecf94fd9bbf6dd15449ec89225fd4e40937cb9528ac79442b41
Tx public key: 66f73ba2b867f4059ae9da15cf07d5288c9ba6a8a1982efaaa1e519d19a042be
Timestamp: 1645019378 Timestamp [UCT]: 2022-02-16 13:49:38 Age [y:d:h:m:s]: 02:326:08:23:38
Block: 439889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 752564 RingCT/type: yes/0
Extra: 0166f73ba2b867f4059ae9da15cf07d5288c9ba6a8a1982efaaa1e519d19a042be0211000000035eb576c5000000000000000000

1 output(s) for total of 21.402545548000 dcy

stealth address amount amount idx
00: 8d405a8a724eb2d22be19d5edd8ac7d603e6636faa8c6f2f033b37839393ca84 21.402545548000 852120 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": 439899, "vin": [ { "gen": { "height": 439889 } } ], "vout": [ { "amount": 21402545548, "target": { "key": "8d405a8a724eb2d22be19d5edd8ac7d603e6636faa8c6f2f033b37839393ca84" } } ], "extra": [ 1, 102, 247, 59, 162, 184, 103, 244, 5, 154, 233, 218, 21, 207, 7, 213, 40, 140, 155, 166, 168, 161, 152, 46, 250, 170, 30, 81, 157, 25, 160, 66, 190, 2, 17, 0, 0, 0, 3, 94, 181, 118, 197, 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