Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4adf076c10dbc52944ce1e1b92f86953400e2afe06c4e0a533dfdbec6bf701c

Tx prefix hash: 0e5ae05ca9feb5d3b8c9687a606522ee96bf845c4f60f50fb8205d87b975cb9b
Tx public key: 809751c71266c31ea4252dafa0ab127fedd76282664509a91c48a72f5b2dbac4
Timestamp: 1721703200 Timestamp [UCT]: 2024-07-23 02:53:20 Age [y:d:h:m:s]: 00:263:18:15:50
Block: 1071667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188430 RingCT/type: yes/0
Extra: 01809751c71266c31ea4252dafa0ab127fedd76282664509a91c48a72f5b2dbac402110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1e49510d525ef0f518c3fa9cefc79635fdca1f0551eacda105410befeca91e6 0.600000000000 1543978 of 15

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": 1071677, "vin": [ { "gen": { "height": 1071667 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1e49510d525ef0f518c3fa9cefc79635fdca1f0551eacda105410befeca91e6" } } ], "extra": [ 1, 128, 151, 81, 199, 18, 102, 195, 30, 164, 37, 45, 175, 160, 171, 18, 127, 237, 215, 98, 130, 102, 69, 9, 169, 28, 72, 167, 47, 91, 45, 186, 196, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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