Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99dac1f2712f9592438a8e63ba3645df91018d035ad5f38448cc7c76fd1de4bb

Tx prefix hash: 65222408c4f0d4d157cbe71551b5114e76d1b10de150550efa288cd75ca028ac
Tx public key: 91aa949902cba8879ae9f643915c9c06cec5a5e2bdb880b28d3670629b48a582
Timestamp: 1577530638 Timestamp [UCT]: 2019-12-28 10:57:18 Age [y:d:h:m:s]: 05:148:10:28:50
Block: 33413 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1256042 RingCT/type: yes/0
Extra: 0191aa949902cba8879ae9f643915c9c06cec5a5e2bdb880b28d3670629b48a5820211000000014943cd9f000000000000000000

1 output(s) for total of 475.660647906000 dcy

stealth address amount amount idx
00: 3a19c9244e21a950f5f8fd10287418a920587482d50d9cf2ef2388a85cbac1d7 475.660647906000 55936 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": 33423, "vin": [ { "gen": { "height": 33413 } } ], "vout": [ { "amount": 475660647906, "target": { "key": "3a19c9244e21a950f5f8fd10287418a920587482d50d9cf2ef2388a85cbac1d7" } } ], "extra": [ 1, 145, 170, 148, 153, 2, 203, 168, 135, 154, 233, 246, 67, 145, 92, 156, 6, 206, 197, 165, 226, 189, 184, 128, 178, 141, 54, 112, 98, 155, 72, 165, 130, 2, 17, 0, 0, 0, 1, 73, 67, 205, 159, 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