Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f385e7e907fea82f25d92bb147f63c7b8a5daa1aee2767e6a4b034cd5fa65e5

Tx prefix hash: d5ff868d793e1ceffe27f37c75338a723ab8ea0a7197430fe9137ab235ac9add
Tx public key: ca6d7da879471ea5624deb6c702165ded5159ea7f71734ea5e294c432a1ce2fb
Timestamp: 1695506806 Timestamp [UCT]: 2023-09-23 22:06:46 Age [y:d:h:m:s]: 01:123:13:17:06
Block: 854689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349554 RingCT/type: yes/0
Extra: 01ca6d7da879471ea5624deb6c702165ded5159ea7f71734ea5e294c432a1ce2fb02110000000133af99f4000000000000000000

1 output(s) for total of 0.903775563000 dcy

stealth address amount amount idx
00: 1b7b03132742c5999b82a77406c117a40d8ad095be8b0777a68731b0348ea674 0.903775563000 1308675 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": 854699, "vin": [ { "gen": { "height": 854689 } } ], "vout": [ { "amount": 903775563, "target": { "key": "1b7b03132742c5999b82a77406c117a40d8ad095be8b0777a68731b0348ea674" } } ], "extra": [ 1, 202, 109, 125, 168, 121, 71, 30, 165, 98, 77, 235, 108, 112, 33, 101, 222, 213, 21, 158, 167, 247, 23, 52, 234, 94, 41, 76, 67, 42, 28, 226, 251, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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