Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16b599cea65dafd6e06b6d730e9473949eff5c60a9a90a7473350732eea1dcee

Tx prefix hash: a8dd1d01673adca9f98fef8d9fd6629465ba8df6b2f4964179d7f3eb537314de
Tx public key: c3afffa51ecc8f732878cf95546796635eabbcdf43cdcc4c85e6a0f81b70fee5
Timestamp: 1607407122 Timestamp [UCT]: 2020-12-08 05:58:42 Age [y:d:h:m:s]: 03:334:13:53:22
Block: 157907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 990115 RingCT/type: yes/0
Extra: 01c3afffa51ecc8f732878cf95546796635eabbcdf43cdcc4c85e6a0f81b70fee5021100000461bf67086c000000000000000000

1 output(s) for total of 183.987891401000 dcy

stealth address amount amount idx
00: a8407700cc64081b9b6081e5fbc18c0b4655e6c1f2d33154595d0968a9e6e053 183.987891401000 272820 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": 157917, "vin": [ { "gen": { "height": 157907 } } ], "vout": [ { "amount": 183987891401, "target": { "key": "a8407700cc64081b9b6081e5fbc18c0b4655e6c1f2d33154595d0968a9e6e053" } } ], "extra": [ 1, 195, 175, 255, 165, 30, 204, 143, 115, 40, 120, 207, 149, 84, 103, 150, 99, 94, 171, 188, 223, 67, 205, 204, 76, 133, 230, 160, 248, 27, 112, 254, 229, 2, 17, 0, 0, 4, 97, 191, 103, 8, 108, 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