Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3aa3d40020584a2be78f8f217d9b5d06c73adc02d8903a79be75e9346e37ef16

Tx prefix hash: 8a49c42d2689f56c68665a1bb62543828e229996949a5ca470ce3161cb15fe32
Tx public key: 0b8e9bd499639ad72e2242d0ba6af0e53dc5b7f1c2a4d761eb2e2e764da1050a
Timestamp: 1590366650 Timestamp [UCT]: 2020-05-25 00:30:50 Age [y:d:h:m:s]: 04:226:03:40:44
Block: 102951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1087546 RingCT/type: yes/0
Extra: 010b8e9bd499639ad72e2242d0ba6af0e53dc5b7f1c2a4d761eb2e2e764da1050a02110000003cd81c26c0000000000000000000

1 output(s) for total of 279.836199154000 dcy

stealth address amount amount idx
00: 49dbac536bad85ef51dfcdcec51a5b4d9190d3c0f6aefacdd42cb09247939ae1 279.836199154000 180708 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": 102961, "vin": [ { "gen": { "height": 102951 } } ], "vout": [ { "amount": 279836199154, "target": { "key": "49dbac536bad85ef51dfcdcec51a5b4d9190d3c0f6aefacdd42cb09247939ae1" } } ], "extra": [ 1, 11, 142, 155, 212, 153, 99, 154, 215, 46, 34, 66, 208, 186, 106, 240, 229, 61, 197, 183, 241, 194, 164, 215, 97, 235, 46, 46, 118, 77, 161, 5, 10, 2, 17, 0, 0, 0, 60, 216, 28, 38, 192, 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