Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65a078c7d40859f5111e3ba191bc5b786491a95041579682e44e8193b94e4d0b

Tx prefix hash: 374f0e714a136106f5a3145597bd75841ca3af790a2aed612bf3a29d0f236840
Tx public key: e6afb78fe8bf21424c8640c8cbda228ef4cc5de2e702832880c7e2add5efc1dd
Timestamp: 1685000267 Timestamp [UCT]: 2023-05-25 07:37:47 Age [y:d:h:m:s]: 01:191:20:57:16
Block: 767645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398534 RingCT/type: yes/0
Extra: 01e6afb78fe8bf21424c8640c8cbda228ef4cc5de2e702832880c7e2add5efc1dd021100000002e6d27f9c000000000000000000

1 output(s) for total of 1.755794271000 dcy

stealth address amount amount idx
00: 0141bd7d3be534db85c7b384b766cef8069517c18373c34a66fb18232cec3014 1.755794271000 1216776 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": 767655, "vin": [ { "gen": { "height": 767645 } } ], "vout": [ { "amount": 1755794271, "target": { "key": "0141bd7d3be534db85c7b384b766cef8069517c18373c34a66fb18232cec3014" } } ], "extra": [ 1, 230, 175, 183, 143, 232, 191, 33, 66, 76, 134, 64, 200, 203, 218, 34, 142, 244, 204, 93, 226, 231, 2, 131, 40, 128, 199, 226, 173, 213, 239, 193, 221, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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