Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7021685ea95ee0cee8b703c08fab773b13376ebc4a71567d0965927124690048

Tx prefix hash: ca65748784b66e9f4394c3326c8b1e2cc66f84d64ca998a8d6b3afbc38495eb5
Tx public key: cb81d876e5b3ff9628071c865af9f44d9c5a993e0fc05bc65902c20199e6ddac
Timestamp: 1580733110 Timestamp [UCT]: 2020-02-03 12:31:50 Age [y:d:h:m:s]: 04:154:01:50:34
Block: 57885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1001240 RingCT/type: yes/0
Extra: 01cb81d876e5b3ff9628071c865af9f44d9c5a993e0fc05bc65902c20199e6ddac021100000031e88dac00000000000000000000

1 output(s) for total of 394.642439636000 dcy

stealth address amount amount idx
00: 9ec615a051fdf4a1d76ca13fd57b80268e743ddaf566307ef08f4abebdc1ff93 394.642439636000 107050 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": 57895, "vin": [ { "gen": { "height": 57885 } } ], "vout": [ { "amount": 394642439636, "target": { "key": "9ec615a051fdf4a1d76ca13fd57b80268e743ddaf566307ef08f4abebdc1ff93" } } ], "extra": [ 1, 203, 129, 216, 118, 229, 179, 255, 150, 40, 7, 28, 134, 90, 249, 244, 77, 156, 90, 153, 62, 15, 192, 91, 198, 89, 2, 194, 1, 153, 230, 221, 172, 2, 17, 0, 0, 0, 49, 232, 141, 172, 0, 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